Route Management

ABSTRACT

Locational tracking aids emergency management plans. Occupants of a building or campus are determined based on presence or detection of wireless devices. When an emergency occurs, the occupants may move to safety based on the current locations of their wireless devices.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.15/406,679 filed Jan. 14, 2017 and since issued as U.S. Pat. No. ______,which is a continuation of U.S. application Ser. No. 14/808,213 filedJul. 24, 2015 and since issued as U.S. Pat. No. 9,582,841, with bothapplications incorporated herein by reference in their entireties. Thisapplication also relates to the following co-pending applications, whichare all incorporated herein by reference in their entireties: U.S.application Ser. No. 14/666,356 filed Mar. 24, 2015; U.S. applicationSer. No. 14/666,361 filed Mar. 24, 2015; and U.S. application Ser. No.14/684,338 filed Apr. 11, 2015.

BACKGROUND

First responders need accurate information. When emergency personnelencounter a rescue situation, real time information describing occupantshelps focus the rescue efforts. Accurate information fosters quickdecisions that save lives.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

The features, aspects, and advantages of the exemplary embodiments areunderstood when the following Detailed Description is read withreference to the accompanying drawings, wherein:

FIGS. 1-5 are simplified illustrations of an environment in whichexemplary embodiments may be implemented;

FIGS. 6-7 illustrate wireless detection, according to exemplaryembodiments;

FIG. 8 is a more detailed illustration of the operating environment,according to exemplary embodiments;

FIGS. 9-13 illustrate locational tracking, according to exemplaryembodiments;

FIGS. 14-15 illustrate a listing of occupants, according to exemplaryembodiments;

FIG. 16 is an illustration of responder credentials, according toexemplary embodiments;

FIGS. 17-18 illustrate a database of personnel, according to exemplaryembodiments;

FIG. 19 further illustrates the listing of occupants, according toexemplary embodiments;

FIGS. 20-21 illustrate a personalized instruction, according toexemplary embodiments;

FIGS. 22-23 illustrate a personalized evacuation route, according toexemplary embodiments;

FIGS. 24-26 illustrate waypoints, according to exemplary embodiments;

FIG. 27 illustrates lock instructions, according to exemplaryembodiments;

FIG. 28 illustrates elevator summons, according to exemplaryembodiments;

FIG. 29 illustrates a personnel directory, according to exemplaryembodiments;

FIG. 30 illustrates an overall database scheme, according to exemplaryembodiments;

FIG. 31 is a flowchart illustrating an algorithm for emergencymanagement, according to exemplary embodiments; and

FIGS. 32-37 depict still more operating environments for additionalaspects of the exemplary embodiments.

DETAILED DESCRIPTION

The exemplary embodiments will now be described more fully hereinafterwith reference to the accompanying drawings. The exemplary embodimentsmay, however, be embodied in many different forms and should not beconstrued as limited to the embodiments set forth herein. Theseembodiments are provided so that this disclosure will be thorough andcomplete and will fully convey the exemplary embodiments to those ofordinary skill in the art. Moreover, all statements herein recitingembodiments, as well as specific examples thereof, are intended toencompass both structural and functional equivalents thereof.Additionally, it is intended that such equivalents include bothcurrently known equivalents as well as equivalents developed in thefuture (i.e., any elements developed that perform the same function,regardless of structure).

Thus, for example, it will be appreciated by those of ordinary skill inthe art that the diagrams, schematics, illustrations, and the likerepresent conceptual views or processes illustrating the exemplaryembodiments. The functions of the various elements shown in the figuresmay be provided through the use of dedicated hardware as well ashardware capable of executing associated software. Those of ordinaryskill in the art further understand that the exemplary hardware,software, processes, methods, and/or operating systems described hereinare for illustrative purposes and, thus, are not intended to be limitedto any particular named manufacturer.

As used herein, the singular forms “a,” “an,” and “the” are intended toinclude the plural forms as well, unless expressly stated otherwise. Itwill be further understood that the terms “includes,” “comprises,”“including,” and/or “comprising,” when used in this specification,specify the presence of stated features, integers, steps, operations,elements, and/or components, but do not preclude the presence oraddition of one or more other features, integers, steps, operations,elements, components, and/or groups thereof. It will be understood thatwhen an element is referred to as being “connected” or “coupled” toanother element, it can be directly connected or coupled to the otherelement or intervening elements may be present. Furthermore, “connected”or “coupled” as used herein may include wirelessly connected or coupled.As used herein, the term “and/or” includes any and all combinations ofone or more of the associated listed items.

It will also be understood that, although the terms first, second, etc.may be used herein to describe various elements, these elements shouldnot be limited by these terms. These terms are only used to distinguishone element from another. For example, a first device could be termed asecond device, and, similarly, a second device could be termed a firstdevice without departing from the teachings of the disclosure.

FIGS. 1-5 are simplified illustrations of an environment in whichexemplary embodiments may be implemented. FIG. 1 illustrates anemergency situation in which first responders 20 arrive at a building22. Ordinarily the first responders 20 have no knowledge of who isinside the building 22. Here, though, the first responders 20 may accessa security server 24 that maintains an occupancy database 26. Theoccupancy database 26 contains occupancy information 28 describing theoccupants inside the building 22. That is, the occupancy information 28may identify each occupant by a name 30 and a current location 32 insidethe building 22. The current location 32 may even be identified byvertical floor 34 and a horizontal position 36 on the vertical floor 34,such as a room or desk. The first responders 20 may thus quickly andeasily use any computer or mobile communications device to query thesecurity server 24 for the current occupancy information 28 describingthe occupants inside the building 22. The security server may thengenerate a listing 40 of occupants currently located inside or even nearthe building 22. The listing 40 of occupants lists the name 30 and thecurrent location 32 of each person (and even pets) associated with thebuilding 22. The listing 40 of occupants may even include a digitalimage 42 of each occupant and various counts 44 of the occupants, suchas by floor, room, and total. The occupancy information 28 is compliedusing wireless tracking technologies and network registrations, whichlater paragraphs will explain. Indeed, exemplary embodiments may alsocomply with the Health Insurance Portability and Accountability Act(“HIPPA”) of 1996 that protects the confidentiality and security ofhealthcare information. For example, the occupancy information 28 mayretrieve and detail healthcare information that is important to thefirst responders 20, such as a pregnant occupant, visually or hearingimpaired occupant, or a physical limitation. So, when the firstresponders 20 receive the occupancy information 28, the first responders20 may thus concentrate their rescue efforts on the current locations 32and immediate needs of the occupants.

FIG. 2 illustrates personalized instructions. As the occupancy database26 maintains the current location 32 of each occupant, exemplaryembodiments may send a personalized instruction 50 to each occupant. Forexample, suppose an occupant carries a mobile smartphone 52. As theoccupant moves within the building 22, the security server 24 tracks themovements of the occupant's smartphone 52 using wireless trackingtechnologies and network registrations (again, as later paragraphs willexplain). During an emergency situation, the security server 24 may thusemail or text the personalized instruction 50 to the occupant'ssmartphone 52. The personalized instruction 50 may be based onlocational rules, such as predetermined text associated with the currentlocations 32 of the occupant and/or pre-assigned roles and tasks (suchas a group leader or designated defibrillator operator), as laterparagraphs will explain. Because the security server 24 monitors thecurrent location 32 of the occupant's smartphone 52, the security server24 may even generate and send a personalized evacuation route 54. Thatis, the occupant may be instructed to evacuate the building 22 byfollowing the personalized evacuation route 54, based on the currentlocation 32 of the occupant's smartphone 52. The occupant may thus beinstructed to proceed to a particular hallway or stairwell that isclosest and safest, based on the current location 32 of the occupant'ssmartphone 52. In other situations the occupant may be instructed tobarricade in a particular room, based on the situation and the currentlocation 32 of the occupant's smartphone 52. Other occupants, though,may receive different instructions, again based on the current locations32 of their corresponding smartphones. Different occupants may thusreceive different personalized instructions 50, all individuallydetermined from the current location 32 of their respective smartphones.Messages may also be auto-generated and broadcasted to any or alloccupants.

FIG. 3 illustrates centralized crisis management. Because the securityserver 24 monitors the current location 32 of each occupant's smartphone52, the security server 24 may implement much faster emergencymanagement plans than humanly possible. For example, the security server24 may select certain occupants to receive specialized emergencyinstructions. A group leader, for example, may be pre-chosen based ontraining or expertise, as later paragraphs will explain. However, thegroup leader may also be selected ad hoc and instructed to lead otheroccupants to safety, perhaps again by following the personalizedevacuation route 54. Suppose, for example, multiple occupants share thesame or similar current location 32, as reported by their respectivesmartphones 52. The security server 24 may thus form an ad hoc group 56and nominate or select one of the smartphones 52 to receive thepersonalized instructions 50, thus leading the group 56 to safety.Exemplary embodiments may thus reduce network and wireless packettraffic by selecting a leader to receive messages and instructions. Anyleader may preferably be chosen based on training or other profilequalifications, as detailed in a database 60 of personnel (as laterparagraphs will explain).

Human flow 70 may be monitored. As many people carry a mobilesmartphone, the security server 24 may monitor the human flow 70 of theoccupants along hallways, stairwells, and other corridors within thebuilding 22. The human flow 70 may be measured, or counted, based on themovement of the occupants' mobile devices (such as smartphones andwearables). The security server 24 may thus count or sum the mobiledevices in an area having the same, or similar current location 32. Asthe count or sum changes with time, a rate (such as the number of mobiledevices per second) of the human flow 70 may be determined. Particularoccupants or groups may thus be directed along different evacuationroutes 54, based on the current location 32 and the human flow 70.Unsafe bottleneck congestions may thus be avoided, based on a safethreshold flow associated with an area. Indeed, most areas may onlysafely convey a maximum human flow 70, as doorways and stairwells oftencreate dangerous stampede situations. Traffic may be moved away fromdangerous areas or hazards. Paths may be created or opened for the firstresponders to move through crowds. People with special needs may bedirected along different paths to different locations. Occupants maythus receive individual electronic texts, emails, calls, or othernotifications according to the current location 32 of their smartphone52. Exemplary embodiments may thus divert the human flow 70 from onearea to another area in order to avoid congestion and standstill.Exemplary embodiments may thus monitor the human flow 70 to move theoccupants to, or away, from locations, thus auto-directing people tosafety.

FIG. 4 illustrates emergency collaboration. Here exemplary embodimentsmay assign tasks 80 to certain individuals, based on the currentlocation 32 of their smartphone 52. Some of the occupants, for example,may have specialized qualifications 82 that may be relied upon duringemergency situations. For example, some occupants may have medicaltraining. Other occupants may have technical knowledge. When thesecurity server 24 consults the database 60 of personnel, the databaseinformation may reveal specialized qualifications 82. Some occupants maythus be selected to inspect one or more rooms for stray people. Someoccupants may be selected to repair equipment. Whatever the task 80,individuals and teams may be assigned based on their qualifications 82and the current location 32 of their smartphone 52 or other wirelessdevice.

Exemplary embodiments thus provide real time emergency management. Aseach occupant's current location 32 is known (both vertically andhorizontally), the security server 24 may track the directions andplaces the occupants are flowing. Logical rules 84 may thus be executedto ensure safe, orderly, and quick movement. Access to the database 60of personnel also reveals what occupants require specialized needs,equipment, or pathways. The security server 24 may thus generate thepersonalized instruction 50 to help ensure a safe and capable rescue.For example, an occupant in a wheelchair may be directed along herpersonalized evacuation route 54 to a ramp or elevator, based on thecurrent location 32 of the occupant's smartphone 52. Frail occupants mayalso be directed to an elevator, while more physically able occupantsmay be directed to a stairwell, all based on the current location 32 ofthe occupant's smartphone 52 and their profile information 90 in thedatabase 60 of personnel. Electronic maps 92 may even be generated, thusproviding the emergency first responders with visual confirmation of thecurrent location 32 of each occupant. Rooms and floors may thus bequickly and methodically cleared.

Exemplary embodiments provide intelligent analytics. The occupancydatabase 26 provides a very accurate, real time picture of the occupantsin the building 22. As the occupants move about the building 22, theoccupancy database 26 tracks the occupants' movements in real time.Individuals may thus be located for quick recovery. As the occupantsmove, exemplary embodiments may monitor the human flow 70 to ensure safeand orderly movement. Individual occupants may receive the personalizedinstructions 50 to further ensure their safe and quick movement. Tasks80 may also be individually assigned to ensure everyone is found andmoved to safety. The first responders 20 may thus concentrate theirefforts on the occupants not located or too injured to move. Indeed,two-way communications may be established with any occupant to furtherensure discovery and safety.

FIG. 5 illustrates a personnel directory 100. Even though FIGS. 1-4illustrate emergency services, the occupancy database 26 may be utilizedfor more general, everyday operations. For example, each occupant'scurrent location 32, as tracked by the occupancy database 26, may beadded as an entry to the personnel directory 100. As the reader mayunderstand, many organizations maintain and even publish a paper orelectronic directory listing of employees, contractors, and otherpersonnel. Exemplary embodiments may thus keep the personnel directory100 updated with the current location 32 of each organizational member.Here, though, the personnel directory 100 preferably lacks at least someof the personal profile information 90. Most personnel do not want theirsocial security number, physical/mental concerns and abilities, andemergency contacts revealed to others. Even though the database 60 ofpersonnel may contain a rich profile of each person, the personneldirectory 100 usually only provides limited contact information 102. Thesecurity server 24 may thus electronically copy the entry detailing thecurrent location 32 in the occupancy database 26 to another databaseentry in the personnel directory 100. The personnel directory 100 maythus contain electronic entries detailing each employee's, contractor's,or other person's contact information 102 and their current location 32,as determined by their smartphone 52 or other mobile wireless device.The smartphone 52, for example, may store a software application thatprovides functionality for an electronic security badge that ensurestracking of the occupant's movements.

Exemplary embodiments thus reveal real time location information.Conventional employee directories are stale and static, failing toreveal dynamic information. Indeed, most directories may only list aparticular building, room, and/or department, which is often meaninglessin today's mobile communications environment. The personnel directory100 thus makes each person's current location 32 available to all,further fostering collaboration as activities change during the day.

The personnel directory 100 is thus automatically updated. Eachemployee's, contractor's, or other person's current location 32 may thusbe logged, even if not currently working in the building 22. Indeed,exemplary embodiments may even generate a historical location 104, basedon historical location information logged over time. Some employees mayhave a desk or office and, yet, spend much working time in a lab orfield environment. The personnel directory 100 may thus beelectronically published to include both the current location 32 and thehistorical location 104, which may differ at different times of day orday of week. Again, tracking both the current location 32 and thehistorical location 104 promotes face-to-face collaboration and spawnsinnovation.

FIGS. 6-7 illustrate wireless detection, according to exemplaryembodiments. Exemplary embodiments track the occupants of the building22, based on wireless detection of their mobile devices. FIG. 6 thusillustrates a human user 110 in a lobby 112 of the building 22. Thehuman user 110 may work within the building 22, or the human user 110may be visiting someone within the building 22. The human user 110, inshort, may be an employee, a visitor, a contractor, a tenant, or a guestrequesting entry into the building 22. For simplicity, the human user110 will mainly be described as an occupant 110. When the occupant 110nears or enters the building 22, exemplary embodiments detect thewireless presence of the occupant's mobile device 114, such as hersmartphone 52. That is, if the occupant's smartphone 52 is recognized,then exemplary embodiments may permit the human occupant 110 to entermore secure areas within the building 22. However, if the occupant'ssmartphone 52 is unrecognized, then exemplary embodiments may requiremore authentication credentials or additional measures. Exemplaryembodiments, for example, may “push” electronic notifications to theoccupant's smartphone 52, thus forcing the occupant to furtherauthenticate.

FIG. 7 illustrates wireless presence. When the occupant enters any areaof the building 22, the occupant's smartphone 52 may attempt to access awireless network 120 serving the area. As the reader likely understands,many people carry a smartphone or other wireless device 114 thatinterfaces with wireless networks. So, when the occupant's smartphone 52operates within any area of the building 22, the smartphone 52 mayestablish wireless communication with the wireless network 120. Thesmartphone 52, for example, may request access or permission to awireless local area network (such as WI-FI®) serving a floor, room, orany other area.

Databases may be updated. Once the wireless network 120 detects theradio presence of the occupant's smartphone 52, the security server 24may determine the current location 32 associated with the occupant'ssmartphone 52. The security server 24 may then log the current location32 in the occupancy database 26. The security server 24 may also consultthe database 60 of personnel and retrieve the profile information 90that is associated with the occupant's smartphone 52. Exemplaryembodiments may thus authorize and monitor the occupant, based on hersmartphone 52.

Exemplary embodiments thus monitor the locations of wireless devices inthe building 22. Wireless detection of any mobile device may thus beused to authorize entry and to track movements. Even though FIGS. 6-7primarily illustrate the occupant's smartphone 52, exemplary embodimentsmay utilize any wired or wireless device (as later paragraphs willexplain). Indeed, badges, watches, and other wearable smart devices maybe wirelessly tracked throughout the building 22.

FIG. 8 is a more detailed illustration of the operating environment,according to exemplary embodiments. FIG. 8 illustrates presencedetection of the occupant's smartphone 52. When the smartphone 52 entersany area, the smartphone 52 may establish wireless communication withthe wireless network 120 serving the area. The smartphone 52, forexample, may request access or permission to a wireless local areanetwork (such as WI-FI®), wide area cellular network, or any othernetwork. The wireless network 120 may only recognize, ortransmit/receive, using a particular frequency or band. The smartphone52 may thus instruct its transceiver (not shown for simplicity) towirelessly request access permission using the electromagnetic frequencyband, channel, or standard required by the wireless network 120.

The security server 24 may be notified. When the wireless network 120detects the smartphone 52, exemplary embodiments may inform the securityserver 24. That is, the smartphone 52 may send an access request to anaccess device 122 serving the wireless network 120. FIG. 8 illustratesthe access device 122 as a wireless router 124, which commonly servesmany residential and business WI-FI® networks. However, the accessdevice 122 may be any network interface to an access network, such as agateway, cable modem, or DSL modem. Regardless, the smartphone 52broadcasts an electronic request that seeks access permission to thewireless network 120. When the access device 122 receives the accessrequest, the access device 122 may send a packetized access notification126 into a communications network 128 for routing and delivery to anetwork address associated with the security server 24. The wirelessrouter 124, for example, may store or execute code or programming thatforces or commands the access notification 126 when any device attemptsto access the wireless network 120. The access notification 126 may thusalert the security server 24 to the radio frequency presence of theoccupant's smartphone 52. The access notification 126 may furtherinclude information that uniquely identifies the smartphone 52, such asdata representing a cellular identifier 130. While any alphanumericcombination may uniquely identify the smartphone 52, FIG. 8 illustratesthe smartphone's cellular telephone number (or “CTN”) 132, InternationalMobile Subscriber Identity (or “IMSI”) 134, or Mobile StationInternational Subscriber Directory Number (“MSISDN”) 136. Whenever themobile smartphone 52 sends messages or information, the smartphone 52may include or self-report its CTN 132, IMSI 134, and/or MSISDN 136.

The security server 24 may authorize the smartphone 52. The securityserver 24 has a processor 140 (e.g., “μP”), application specificintegrated circuit (ASIC), or other component that executes a securityalgorithm 142 stored in a local memory 144. The security algorithm 142instructs the processor 140 to perform operations, such as receiving andprocessing information received from a network interface to thecommunications network 128. The information may be received as packetsof data according to a packet protocol (such as any of the InternetProtocols). The packets of data contain bits or bytes of data describingthe contents, or payload, of a message. A header of each packet of datamay contain routing information identifying an origination addressand/or a destination address. The security algorithm 142, for example,may instruct the processor 140 to inspect the packetized accessnotification 126 for the cellular identifier 130 of the occupant'ssmartphone 52 requesting access to the wireless network 120.

Exemplary embodiments may be applied regardless of networkingenvironment. Exemplary embodiments may be easily adapted to stationaryor mobile devices having cellular, WI-FI®, near field, and/or BLUETOOTH®capability. Exemplary embodiments may be applied to mobile devicesutilizing any portion of the electromagnetic spectrum and any signalingstandard (such as the IEEE 802 family of standards, GSM/CDMA/TDMA or anycellular standard, and/or the ISM band). Exemplary embodiments, however,may be applied to any processor-controlled device operating in theradio-frequency domain and/or the Internet Protocol (IP) domain.Exemplary embodiments may be applied to any processor-controlled deviceutilizing a distributed computing network, such as the Internet(sometimes alternatively known as the “World Wide Web”), an intranet, alocal-area network (LAN), and/or a wide-area network (WAN). Exemplaryembodiments may be applied to any processor-controlled device utilizingpower line technologies, in which signals are communicated viaelectrical wiring. Indeed, exemplary embodiments may be appliedregardless of physical componentry, physical configuration, orcommunications standard(s).

Exemplary embodiments may utilize any processing component,configuration, or system. Any processor could be multiple processors,which could include distributed processors or parallel processors in asingle machine or multiple machines. The processor can be used insupporting a virtual processing environment. The processor could includea state machine, application specific integrated circuit (ASIC),programmable gate array (PGA) including a Field PGA, or state machine.When any of the processors execute instructions to perform “operations”,this could include the processor performing the operations directlyand/or facilitating, directing, or cooperating with another device orcomponent to perform the operations.

FIGS. 9-13 illustrate locational tracking, according to exemplaryembodiments. Once the smartphone 52 is wirelessly detected, exemplaryembodiments may log the movements for analysis. FIG. 9, for example,illustrates global positioning system (“GPS”) tracking. As the readermay understand, the smartphone 52 may randomly or periodically reportits current location 32 as global positioning system information 150.FIG. 9 illustrates the smartphone 52 reporting its current location 32into the wireless WI-FI® network 120, which the access device 122 mayforward to the security server 24. The current location 32, however, maybe routed into a cellular network for delivery to the network addressassociated with the security server 24. Regardless, when the securityserver 24 receives the current location 32, the security server 24 alsoreceives the cellular identifier 130 associated with the smartphone 52.The security algorithm 142 may thus cause the security server 24 to addor update the occupancy database 26 with the current location 32. Thesecurity server 24 may thus add an electronic database associationbetween the cellular identifier 130 and the global positioning systeminformation 150 reported by the smartphone 52.

FIG. 10 further illustrates the occupancy database 26. The occupancydatabase 26 logs the locations 32 reported by occupant's smartphone 52.FIG. 10 illustrates the occupancy database 26 as a table 152 thatelectronically maps, relates, or associates different current locations32 to the cellular identifier 130 of the occupant's smartphone 52. Thesmartphone 52, though, may be additionally or alternatively uniquelyidentified by a network address, a manufacturer's serial number, or anyother alphanumeric combination. The occupancy database 26 is illustratedas being locally stored in the memory 144 of the security server 24, butsome or all of the electronic database entries may be remotelymaintained at some other server or location in the communicationsnetwork (illustrated as reference numeral 128 in FIG. 8). Although FIG.10 only illustrates a few entries, in practice the occupancy database 26may contain many entries that richly detail the movements of thesmartphone 52.

FIG. 11 illustrates network-wide tracking. As the reader may envision,the occupancy database 26 may be expanded to track the movements of manywireless devices. As employees, contractors, and visitors come and go,the occupancy database 26 may monitor the locations 32 reported by manydifferent wireless devices. FIG. 11 thus illustrates several entriesthat associate different cellular identifiers 130 to their correspondinglocations 32. While FIG. 11 only illustrates several entries, inpractice the occupancy database 26 may contain many entries that richlydetail the movements of hundreds or thousands of mobile devices.

FIGS. 12-13 illustrate network tracking. Here exemplary embodiments mayuse network recognition to track the current location 32 of theoccupant's smartphone 52. As the reader may understand, GPS signals aresometimes not received, especially when the smartphone 52 operates in anin indoor environment. Moreover, other users may disable GPS locationservices for privacy concerns. Whatever the reason, GPS signals may notbe available or receivable. Exemplary embodiments, then, mayadditionally or alternatively track the current location 32 of theoccupant's smartphone 52 using network identifiers. For example, as theoccupant carries the smartphone 52, the smartphone 52 may wirelesslyencounter different wireless local area networks (e.g., WI-FI®) servingthe different floors, hallways, and/or rooms within the building. Theoccupant's smartphone 52 may also detect other identifiers of othernetworks (such as different cellular network cells). Regardless, thesmartphone 52 may thus request access permission to each wirelessnetwork 120. FIG. 12 thus illustrates the current location 32represented as a service set identifier (or “SSID”) 160 that uniquelyidentifies a WI-FI® network currently proving wireless service to thesmartphone 52. The SSID 160 may be self-reported by the smartphone 52,or the SSID 160 may be reported to the security server 24 (perhaps usingthe access notification 126 send from the access device 122, asexplained with reference to FIG. 8). The access notification 126 mayhave a timestamp 162 that marks a time of requested access to thewireless network 120. Regardless, when the security server 24 receivesthe SSID 160, the security server 24 also receives the cellularidentifier 130 associated with the smartphone 52. As FIG. 13illustrates, the security algorithm 142 may thus cause the securityserver 24 to add or update the occupancy database 26 with the SSID 160.The security server 24 may thus add an electronic database associationbetween the SSID 160, the cellular identifier 130 reported by thesmartphone 52, and the timestamp 162.

Exemplary embodiments thus present an elegant solution. In today'smobile environment, people may be uniquely identified by their mobiledevices (such as the smartphone 52). Employees, tenants, and visitorsmay thus be personally identified merely by carrying their smartphones.The occupancy database 26 thus contains entries that uniquely identifythe wireless devices associated with the occupants. As any wirelessdevice requests network access, the occupancy database 26 logs thecorresponding current location 32. At any time, then, the occupancydatabase 26 provides a real time view of the current locations 32 of theoccupants, as determined by tracking of their wireless devices.

FIGS. 14-15 further illustrate the listing 40 of occupants, according toexemplary embodiments. As this disclosure explained, the firstresponders 20 may remotely access the security server 24. Assume any ofthe first responders 20 also carries a mobile device, such as a tabletcomputer 170. Whenever a first responder 20 needs to learn the occupancyof the building, the first responder's smartphone 52 may send a query172. The query 172 may route into and along the communications network128 to the network address associated with the security server 24. Thequery 172 requests the listing 40 of occupants associated with thebuilding 22. For example, the query 172 may specify a physical/postalstreet address (“123 Main St.”) or building name (“Rockefeller Center”)as a search term. The security server 24 thus queries the occupancydatabase 26 for the search term and retrieves the listing 40 ofoccupants matching the search term. The security server 24 thus sendsthe listing 40 of occupants as a query response to some destination,such as the network address associated with the first responder's tabletcomputer 170. When the first responder's tablet computer 170 receivesthe listing 40 of occupants, the first responder's tablet computer 170may process the listing 40 of occupants for display, such as on itsdisplay device 174. The listing 40 of occupants lists the name 30 andthe current location 32 of each occupant within the building 22, asreported by their respective wireless devices. The current location 32may even be pinpointed to the vertical floor 34 and the horizontalposition 36. The first responders 20 may thus concentrate their rescueefforts on the current locations 32 of the occupants.

FIG. 15 further illustrates the listing 40 of occupants. Here the tabletcomputer 170 processes the listing 40 of occupants for display as agraphical user interface 176. When the security server 24 queries theoccupancy database 26 (as FIG. 14 illustrated), the security server 24may also tally or sum the total count 44 of the occupants currentlylocated within the building 22, even grouped or determined by thevertical floor 34 and their horizontal position 36. The listing 40 ofoccupants may thus identify the occupants in a cafeteria or meetingroom, according to their current location 32. The occupants having thesame or similar current location 32 may be grouped together, perhaps toaid rescue efforts. The listing 40 of occupants may further includegraphical controls and/or website links that further display the namesand images of the occupants (as explained with reference to FIG. 1).

FIG. 16 is an illustration of responder credentials, according toexemplary embodiments. As the reader may understand, the occupancydatabase 26 may be restricted in accessibility. That is, only authorizedpersons may retrieve the information logged in the occupancy database26. Security measures may thus be implemented to avoid rogue access.FIG. 16, for example, illustrates a software application 180 that may berequired for access. The software application 180 is downloaded to thefirst responder's mobile device, such as her tablet computer 170. Thesoftware application 180 contains specialized programming or code thatauthorizes or even allows access to the occupancy database 26. Thesecurity algorithm 142 may thus cooperate with, and even require, thesoftware application 180 in order to access and query the occupancydatabase 26. Indeed, the inventors envision that only authorizedpersonnel (such as police, fire, and other emergency services) wouldhave downloadable access to the software application 180. Moreover,additional security features may also require identification of thefirst responder's tablet computer 170, such as its correspondingcellular identifier 130. If the software application 180 is downloadedto an approved list of cellular identifiers, then the first responder'stablet computer 170 may query for and retrieve the listing 40 ofoccupants.

FIGS. 17-18 illustrate the database 60 of personnel, according toexemplary embodiments. As this disclosure briefly explained, thedatabase 60 of personnel stores names, addresses, images, and/or otherprofile information 90 for employees, contractors, and other personnel.For simplicity the database 60 of personnel is illustrated as a table190 that electronically maps, relates, or associates different personnelto their corresponding profile information 90. For example, an entry mayassociate each person's name 30, address 192, and/or employee number 194to the cellular identifier 130 associated with the person's personalwireless device (such as the smartphone 52 illustrated in FIGS. 1-8).FIG. 17 illustrates the cellular identifier 130 as the cellulartelephone number 132, the IMSI 134, and/or the MSISDN 136. Moreover, thedatabase 60 of personnel may further associate a digital image file 196to the cellular identifier 130, thus allowing retrieval, recognition,and/or analysis of a facial image. The database 60 of personnel isillustrated as being locally stored in the memory 144 of the securityserver 24, but some or all of the database entries may be remotelymaintained at some other server or location in the communicationsnetwork (illustrated as reference numeral 128 in FIG. 8). While FIG. 17only illustrates a few entries, in practice the database 60 of personnelmay contain many electronic entries for hundreds or thousands of people.

As FIG. 18 illustrates, the security server 24 may query the database 60of personnel. When the security server 24 receives the accessnotification 126, the security algorithm 142 causes the security server24 to query for entries that match the query search term(s) detailed ordescribed in the electronic access notification 126. The query searchterm, for example, may be the cellular identifier 130 detailed in theaccess notification 126. If the database 60 of personnel contains amatching entry, then the security server 24 may retrieve the profileinformation 90 having an electronic database association with thecellular identifier 130.

FIG. 19 further illustrates the listing 40 of occupants, according toexemplary embodiments. Here the listing 40 of occupants may besupplemented or augmented with database information retrieved from thedatabase 60 of personnel. For example, the listing 40 of occupants mayinclude the profile information 90 retrieved from the database 60 ofpersonnel (as FIG. 18 illustrated). That is, once the cellularidentifier 130 is known, the corresponding occupant's digital image file196 of her facial image 42 may be incorporated into the listing 40 ofoccupants. The occupant's digital facial image 42 thus provides quickervisual recognition and confirmation. The listing 40 of occupants mayalso include the occupant's home address 192 and emergency contactinformation 198 to alert loved ones and neighbors. The profileinformation 90 may further include health information, medical concerns,medications, and any other information that could aid medical personnelin rendering care. Any profile information 90 desired may beincorporated into the listing 40 of occupants to aid the firstresponders.

FIGS. 20-21 illustrate the personalized instruction 50, according toexemplary embodiments. Once the occupant's current location 32 is known,exemplary embodiments may send the personalized instruction 50. Thepersonalized instruction 50 may be a call, text, email or otherelectronic communication that instructs the occupant (via her smartphone52) to implement some action or plan during the crisis. An emergencyresponder may thus call or text specific instructions to ensure safety.

FIGS. 20-21, though, illustrate a database 200 of instructions. Thedatabase 200 of instructions stores one or more instructions 50 that arepre-configured for the occupant's current location 32, as reported byher smartphone 52. Once the security algorithm 142 determines thecurrent location 32 of the occupant's smartphone 52, the securityalgorithm 142 may instruct the security server 24 to query the database200 of instructions for the corresponding instruction 50. The currentlocation 32, as earlier explained, may be represented as the globalpositioning system information 150 and/or the service set identifier(“SSID 160”) that uniquely identifies the WI-FI® network currentlyproving wireless service to the occupant's smartphone 52. FIG. 20illustrates the database 200 of instructions locally stored in thememory 144 of the security server 24, but some or all of the databaseentries may be remotely maintained at some other server or location inthe communications network 128. FIG. 21 illustrates the database 200 ofinstructions as a table 202 that electronically maps, relates, orassociates different instructions 50 to different locations 32. Thesecurity server 24 executes a database lookup and retrieves thecorresponding instruction 50 that has been pre-configured orpredetermined for the current location 32. Returning to FIG. 20, thesecurity server 24 may then generate an electronic message 204 thatincorporates the instruction 50 (perhaps as text). The security server24 sends the electronic message 204 to the cellular identifier 130 orother network address associated with the occupant's smartphone 52.

Exemplary embodiments may thus include location-based instructions. Asthe occupant carries the mobile smartphone 52, exemplary embodimentstrack the movements of the occupant's smartphone 52. When an emergencysituation occurs, the security server 24 may monitor the smartphone'scurrent location 32 and retrieve the corresponding personalizedinstruction 50. The security server 24 may then electronically notifythe occupant using the electronic message 204. For example, suppose thedatabase 200 of instructions includes entries identifying locations offirst aid kits. As the occupant approaches a first aid kit, the securityserver 24 may personally instruct the occupant to retrieve the first aidkit, based on the proximity of her smartphone 52. Likewise, the database200 of instructions may also include the locations of fire extinguishersand defibrillators. Should any occupant move in proximity to one of thepredetermined locations, the security server 24 may personally instructthe occupant to retrieve the emergency equipment, based on the proximityof her smartphone 52. Other occupants may be instructed to open or closedoors and windows, again based on the proximity of their smartphones.

FIGS. 22-23 illustrate the personalized evacuation route 54, accordingto exemplary embodiments. Once the security algorithm 142 determines thecurrent location 32 of the occupant's smartphone 52, the securityalgorithm 142 may instruct the security server 24 to query a database210 of routes for the corresponding evacuation route 54. The database210 stores one or more evacuation routes 54 that are pre-configured forthe occupant's current location 32, as reported by her smartphone 52.Once the occupant's current location 32 is known, exemplary embodimentsmay retrieve and send the personalized evacuation route 54 to theoccupant's smartphone 52. The current location 32, as earlier explained,may be represented as the global positioning system information 150and/or the service set identifier (“SSID 160”) that uniquely identifiesthe WI-FI® network currently proving wireless service to the occupant'ssmartphone 52. FIG. 22 illustrates the database 210 of routes locallystored in the memory 144 of the security server 24, but some or all ofthe database entries may be remotely maintained at some other server orlocation in the communications network 128. FIG. 23 illustrates thedatabase 210 of routes as a table 212 that electronically maps, relates,or associates different evacuation routes 54 to different locations 32.The security server 24 executes a database lookup and retrieves thecorresponding evacuation route 54 that has been pre-configured orpredetermined for the current location 32. Returning to FIG. 22, thesecurity server 24 may then generate the electronic message 204 thatincorporates the evacuation route 54 (perhaps as text). The securityserver 24 sends the electronic message 204 to the cellular identifier130 or other network address associated with the occupant's smartphone52.

Exemplary embodiments may thus include location-based routings. Duringan emergency situation, the security server 24 may monitor thesmartphone' s current location 32 and retrieve the correspondingevacuation route 54 that is pre-configured for the smartphone' s currentlocation 32. The database 210 of routes may thus have entriesidentifying paths along corridors and stairwells that are pre-approvedfor emergency uses. Paths may be predetermined based on distance and ortime, as some paths may be quicker from different locations. Other pathsmay be predetermined based on safety concerns, as some paths may haveeasier ingress and egress. The predetermined evacuation routes 54, ofcourse, will vary greatly depending on building design, floor layout,and even furniture interior decorating.

Exemplary embodiments thus help alleviate panic. In most emergencysituations the occupants fend for themselves. Here, though, emergencyplans may be developed in advance and planned according to eachindividual, based on the current location 32. Routes 54 may be chosen toensure efficient and maximum movement to safety, especially consideringthe human flow 70 along the corridors of the facility. Groups ofoccupants may be directed along one route, while a different group ofoccupants may be directed along a different route, even if the groupshave similar locations. Indeed, the human flow 70 (e.g., the count ofdevices per unit of time requesting wireless access to the access device122) can provide a quick and accurate measure of capacity along hallwaysand other corridors. Occupants may thus be lead to safe gatheringpoints, whether inside a room or exterior of the building.

FIGS. 24-26 illustrate waypoints, according to exemplary embodiments.Once the predetermined evacuation route 54 is retrieved, the occupantshould walk or ride along the evacuation route 54 to a predeterminedsafe destination. If the occupant strays from the evacuation route 54,the occupant may be endangering him and others. Exemplary embodiments,then, may track the occupant's position or progress along thepredetermined evacuation route 54. FIG. 24 thus illustrates GPSwaypoints 220 along which the smartphone 52 may or must report. That is,the predetermined evacuation route 54 may be defined as a series 222 ofglobal positioning system information 150 from an initial GPS coordinate224 to a final GPS coordinate 226. As the occupant walks the corridorsof the building, the occupant's smartphone 52 may continually,periodically, and/or randomly report its current location 32. FIG. 24illustrates the smartphone 52 reporting its current location 32 into thewireless network 120, which the access device 122 may forward to thesecurity server 24. The current location 32, however, may be routed intoa cellular network for delivery to the network address associated withthe security server 24. Regardless, when the security server 24 receivesthe current location 32, the security server 24 may compare the currentlocation 32 to the GPS waypoints 220 associated with the evacuationroute 54. If the current location 32 matches one of the GPS waypoints(perhaps within a locational tolerance), then the security algorithm 142may conclude that the occupant's smartphone 52 is on track andproceeding as authorized. However, if the current location 32 reportedby the occupant's smartphone 52 fails to match one or any of the GPSwaypoints 220, the security algorithm 142 may generate a securitynotification 228. The security notification 228 may be any electronicmessage that warns the occupant to resume the predetermined evacuationroute 54 to the safe destination, as represented by the final entry orGPS coordinate 226. The security notification 228 may route back to theaccess device 122 for transmission to the network address assigned tothe smartphone 52. However, the security notification 228 may be a shortmessage service (SMS) text message that is sent to the unique cellularidentifier 130 of the visitor's smartphone 52. The security notification228 may further include a correction 230 that puts the occupant back onthe predetermined evacuation route 54 to the destination 226. Moreover,the security server 24 may also copy or forward the securitynotification 228 to a device associated with an emergency responder fornearly immediate human intervention.

FIG. 25 illustrates network waypoints 240. Here exemplary embodimentsmay define the predetermined evacuation route 54 as a series 242 ofservice set identifiers. Each individual service set identifier (or“SSID”) 160 uniquely identifiers a different WI-FI® network serving someportion of the predetermined evacuation route 54 from an initial SSID244 to a final SSID 246 at the safe destination. For example, as theoccupant's smartphone 52 moves along the predetermined evacuation route54, the security server 24 may receive a series of the accessnotifications 126 identifying the corresponding SSID 160. The securityserver 24 may thus compare the SSID 160 to the network waypoints 240associated with the predetermined evacuation route 54. If the currentSSID 160 matches one of the network waypoints 240, then the securityalgorithm 142 may conclude that the occupant's smartphone 52 is on trackand proceeding as authorized. However, if the SSID 160 fails to matchone or any of the network waypoints 240, the security algorithm 142 maygenerate the security notification 228 with the correction 230 (asearlier explained).

The waypoints may be strictly compared. As the occupant evacuates, thesecurity server 24 receives sequential access notifications 126. Thesecurity server 24 may require a strict sequential match with thenetwork waypoints 240. The occupant's smartphone 52, in other words, maybe required to traverse the network waypoints 240 in sequential order,from the first entry SSID 244 to the final destination SSID 246wirelessly serving the safe destination. If the smartphone 52 straysfrom the predetermined evacuation route 54, one of the accessnotifications 126 will identify an SSID 160 not matching the networkwaypoints 240 in the approved evacuation route 54. The smartphone 52, inother words, is requesting wireless access to an unauthorized network,perhaps revealing a dangerous detour. The security algorithm 142 maythus warn the occupant to resume the pre-configured evacuation route 54(as earlier explained).

FIG. 26 illustrates timing requirements. Here each network waypoint 240may also have a corresponding timing parameter 250. FIG. 26 thusillustrates each network waypoint 240 as an SSID/time pairing. That is,each network waypoint 240 may be a network/timing pair of valuesassociated with each successive wireless network 120. As the occupant'ssmartphone 52 travels along the predetermined evacuation route 54, thesecurity server 24 may monitor a speed or time of movement. Each accessnotification 126 may have the timestamp 162 that marks a time ofrequested access to the wireless network 120 (as identified by the SSID160). As the security server 24 sequentially compares the SSID 160 tothe network waypoints 240, the security server 24 may also requirestrict adherence to each corresponding timing parameter 250. Thesecurity server 24, in other words, may initialize a timer 252 withreceipt of the access notification 126. The timer 252 counts up or downto a final value at a receipt of a next access notification 126associated with the same occupant's smartphone 52 (e.g., the cellularidentifier 130). The timer 252, for example, may thus count a time inseconds or minutes between successive access notifications 126 sent fromdifferent access devices 122 along the predetermined evacuation route54. So, not only must each sequential SSID 160 match the networkwaypoints 240, but exemplary embodiments may also require timingcompliance between the successive network waypoints 240. The securityserver 24 may thus compare a current value of the timer 252 to thetiming parameter 250 associated with a next corresponding networkwaypoint 240 in the series 242. If the current value of the timer 252 isless than or equal to the timing parameter 250, then the securityalgorithm 142 may conclude that the occupant's smartphone 52 is on theapproved evacuation route 54 and on track to arrive on time at the finalsafe destination 246. However, if the current value of the timer 252exceeds the timing parameter 250, the security algorithm 142 mayconclude that the occupant will be delayed.

FIG. 27 illustrates lock instructions, according to exemplaryembodiments. As the reader may imagine, some doors should be lockedduring a crisis while other doors should unlock. The security server 24,then, may generate and send a lock instruction 260 to lock or unlock anelectronic lock 262. FIG. 27 illustrates the packetized lock instruction260 routing along the communications network 120 to a network addressassociated with an electronic lock controller 264. The lock instruction260 may thus have an electronic database association with the evacuationroute 54 that is pre-configured for the smartphone's current location32. Exemplary embodiments may thus lock, and/or unlock, doors along theevacuation route 54 to ensure the occupant does not stray off course.For example, if a room or hallway is not along the evacuation route 54,then the security server 24 may lock that corresponding door to prevententry. In other words, only the doors along the predetermined evacuationroute 54 may be operable. Circumstances will of course control differentsituations. When the security server 24 retrieves the evacuation route54, the security server 24 may also retrieve and execute thecorresponding lock instructions 50. The security server 24 may thusinstruct the electronic lock controller 264 to activate physical locks,based on the current location 32 associated with the occupant'ssmartphone 52.

FIG. 28 illustrates elevator summons, according to exemplaryembodiments. As the smartphone 52 traverses the pre-approved evacuationroute 54, at some point elevator service may be required. Some crisismanagement plans may deactivate elevators, thus forcing the occupants toclimb or descend stairs to safety. Other crisis management plans,though, may embrace elevator service as a quick and efficient means ofsafely moving groups of people. Exemplary embodiments may thus track themovements of the occupants' wireless devices and summon elevators atappropriate moments in time or location. FIG. 28, for example,illustrates an elevator command 270 as a data triplet 271 inserted intoone of the network waypoints 240. The elevator command 270 identifieswhich elevator (elevator number or identifier) is summoned for verticaltravel from an entry floor to an exit floor. If a building only has oneelevator, then perhaps the elevator command 270 may be simplified to apair of data values. But many buildings may have multiple elevators,perhaps serving different floors. The elevator command (3, 1, 22), forexample, may call or summon “Elevator #3” to “Floor #1” for lift serviceto “Floor #22.” The opposite elevator command (3, 22, 1) would call“Elevator #3” to “Floor #22” for descend service to “Floor #1.” Eachelevator command 270 may thus be generated for insertion into thepre-determined sequential network waypoints 240. As the smartphone 52satisfies each sequential network waypoint 240, the security server 24may summon the corresponding elevator in the sequence. The securityalgorithm 142 may further initialize the timer 252 to count up or downuntil the summons. Exemplary embodiments, then, may insert the elevatorcommand 270 at appropriate positions and/or times in the sequentialnetwork waypoints 240 and/or the sequential GPS waypoints (illustratedas reference numeral 220 in FIG. 24). As the security server 24 tracksthe smartphone 52, the security server 24 may thus read, retrieve,and/or execute the elevator command 270 as one of the sequential steps.The security server 24 may thus generate an elevator instruction 272that is sent into the communications network 120 for delivery to thenetwork address associated with an elevator controller 274. The elevatorcontroller 274 may then summon the corresponding elevator car 276 toload the occupants.

Exemplary embodiments thus automate crisis management plans. Todaymobile devices may be locationally tracked with precision. Thislocational tracking may thus be used for much quicker decisions thatsave more lives. Exemplary embodiments may thus present each individualoccupant with the predetermined evacuation route 54 to ensure her ownsafety and the safety of others. Moreover, exemplary embodiments mayeven electronically secure doors and windows to limit access, thusfurther ensuring the occupants maintain their individual evacuationroute 54. Exemplary embodiments may even summon elevators for stillfaster evacuation of more people.

FIG. 29 illustrates the personnel directory 100, according to exemplaryembodiments. As this disclosure above explained, the locationalcapabilities may be applied to the personnel directory 100. That is, thepersonnel directory 100 may be updated to reveal each occupant's currentlocation 32, as tracked by the occupancy database 26. FIG. 29 thusillustrates the personnel directory 100 as a table 280 having electronicdatabase associations between different cellular identifiers 130, theircorresponding current location 32, and the organizational member'scontact information 102. The personnel directory 100 may further includeelectronic associations with each member's digital image file 196. Thepersonnel directory 100 may thus be automatically updated with eachemployee's, contractor's, or other member's current location 32.Moreover, as the occupancy database 26 may have historical entries thatlog past locations, the personnel directory 100 may further include anentry for the member's historical location 104, based on historicallocation information logged over time. The security algorithm 142 maydetermine the historical location 104 as a greatest accumulation of timethe same location, thus revealing a lab, field environment, or customeroffice where the most time is accrued. Again, tracking both the currentlocation 32 and the historical location 104 promotes face-to-facecollaboration and spawns innovation.

FIG. 30 illustrates an overall database scheme, according to exemplaryembodiments. Here the security server 24 may access any of the databases(illustrated as reference numerals 26, 60, 100, 200, and 210) to loglocations and to evacuate personnel, as this disclosure explains. Thedatabases may be individually maintained or grouped together, dependingon networking, processing, and storage capabilities.

FIG. 31 is a flowchart illustrating an algorithm for emergencymanagement, according to exemplary embodiments. The current location 32,associated with the cellular identifier 130, is determined (Block 300).The occupancy database 26 is updated with the current location 32 (Block302). The profile information 90 (Block 304), the personal instruction(Block 306), and the evacuation instruction 54 (Block 308) areretrieved. The current location 32 is compared to the GPS or networkwaypoints (Block 310). Electronic locks are activated (Block 312) andelevators are summoned (Block 314). The listing 40 of occupants isgenerated (Block 316).

FIG. 32 illustrates still more exemplary embodiments. FIG. 32 is a moredetailed diagram illustrating a processor-controlled device 350. Asearlier paragraphs explained, exemplary embodiments may partially orentirely operate in any mobile or stationary processor-controlleddevice. FIG. 32, then, illustrates the security algorithm 142 stored ina memory subsystem of the processor-controlled device 350. One or moreprocessors communicate with the memory subsystem and execute either,some, or all applications. Because the processor-controlled device 350is well known to those of ordinary skill in the art, no furtherexplanation is needed.

FIG. 33 depicts other possible operating environments for additionalaspects of the exemplary embodiments. FIG. 33 illustrates the securityalgorithm 142 operating within various other processor-controlleddevices 350. FIG. 33, for example, illustrates a set-top box (“STB”)(352), a personal/digital video recorder (PVR/DVR) 354, a GlobalPositioning System (GPS) device 356, an interactive television 358, atablet computer 360, or any computer system, communications device, orprocessor-controlled device utilizing the processor and/or a digitalsignal processor (DP/DSP) 362. The device 350 may also include watches,radios, vehicle electronics, clocks, printers, gateways,mobile/implantable medical devices, and other apparatuses and systems.Because the architecture and operating principles of the various devices350 are well known, the hardware and software componentry of the variousdevices 350 are not further shown and described.

FIGS. 34-36 are schematics further illustrating the processor-controlleddevice 350, according to exemplary embodiments. FIG. 34 is a blockdiagram of a Subscriber Identity Module 370, while FIGS. 35 and 36illustrate, respectively, the Subscriber Identity Module 370 embodied ina plug 372 and in a card 374. As those of ordinary skill in the artrecognize, the Subscriber Identity Module 370 may be used in conjunctionwith many devices (such as the occupant's smartphone 52, the firstresponder's tablet computer 170, and the processor-controlled device350). The Subscriber Identity Module 370 stores user information (suchas a user's International Mobile Subscriber Identity, the user's K_(i)number, and other user information) and any portion of the securityalgorithm 142. As those of ordinary skill in the art also recognize, theplug 372 and the card 374 each may interface with any mobile orstationary device.

FIG. 34 is a block diagram of the Subscriber Identity Module 370,whether embodied as the plug 372 of FIG. 35 or as the card 374 of FIG.36. Here the Subscriber Identity Module 370 comprises a microprocessor376 (μP) communicating with memory modules 378 via a data bus 380. Thememory modules 328 may include Read Only Memory (ROM) 382, Random AccessMemory (RAM) and or flash memory 384, and ElectricallyErasable-Programmable Read Only Memory (EEPROM) 386. The SubscriberIdentity Module 370 stores some or all of the security algorithm 142 inone or more of the memory modules 378. An Input/Output module 388handles communication between the Subscriber Identity Module 370 and ahost device. Because Subscriber Identity Modules are well known in theart, this patent will not further discuss the operation and thephysical/memory structure of the Subscriber Identity Module 370.

FIG. 37 is a schematic further illustrating the operating environment,according to exemplary embodiments. FIG. 37 is a block diagramillustrating more possible componentry of the processor-controlleddevice 350. The componentry may include one or more radio transceiverunits 400, an antenna 402, a digital baseband chipset 404, and aman/machine interface (MMI) 406. The transceiver unit 400 includestransmitter circuitry 408 and receiver circuitry 410 for receiving andtransmitting radio-frequency (RF) signals. The transceiver unit 400couples to the antenna 402 for converting electrical current to and fromelectromagnetic waves. The digital baseband chipset 404 contains adigital signal processor (DSP) 412 and performs signal processingfunctions for audio (voice) signals and RF signals. As FIG. 37 shows,the digital baseband chipset 404 may also include an on-boardmicroprocessor 414 that interacts with the man/machine interface (MMI)406. The man/machine interface (MMI) 406 may comprise a display device416, a keypad 418, and the Subscriber Identity Module 370. The on-boardmicroprocessor 414 may also interface with the Subscriber IdentityModule 370.

Exemplary embodiments may be applied to any signaling standard. As thoseof ordinary skill in the art recognize, FIGS. 34-37 may illustrate aGlobal System for Mobile (GSM) communications device. That is, thecommunications device may utilize the Global System for Mobile (GSM)communications signaling standard. Those of ordinary skill in the art,however, also recognize that exemplary embodiments are equallyapplicable to any communications device utilizing the Time DivisionMultiple Access signaling standard, the Code Division Multiple Accesssignaling standard, the “dual-mode” GSM-ANSI Interoperability Team(GAIT) signaling standard, or any variant of the GSM/CDMA/TDMA signalingstandard. Exemplary embodiments may also be applied to other standards,such as the I.E.E.E. 802 family of standards, the Industrial,Scientific, and Medical band of the electromagnetic spectrum,BLUETOOTH®, and any other.

Exemplary embodiments may be physically embodied on or in acomputer-readable memory device or other storage medium. Thiscomputer-readable medium, for example, may include CD-ROM, DVD, tape,cassette, floppy disk, optical disk, memory card, memory drive, andlarge-capacity disks. This computer-readable medium, or media, could bedistributed to end-subscribers, licensees, and assignees. A computerprogram product comprises processor-executable instructions forlocational tracking for crisis management, as the above paragraphsexplained.

While the exemplary embodiments have been described with respect tovarious features, aspects, and embodiments, those skilled and unskilledin the art will recognize the exemplary embodiments are not so limited.Other variations, modifications, and alternative embodiments may be madewithout departing from the spirit and scope of the exemplaryembodiments.

1. A system, comprising: a hardware processor; and a memory device, thememory device storing instructions, the instructions when executedcausing the processor to perform operations, the operations comprising:determining a count of wireless devices registered with a wirelessnetwork; querying an electronic database for the count of the wirelessdevices registered with the wireless network, the electronic databaseelectronically associating routes to counts including the count of thewireless devices registered with the wireless network; identifying aroute of the routes in the electronic database that is electronicallyassociated with the count of the wireless devices registered with thewireless network; and monitoring locations associated with the wirelessdevices according to the route identified in the electronic database. 2.The system of claim 1, wherein the operations further comprise sendingthe route to any of the wireless devices registered with the wirelessnetwork.
 3. The system of claim 1, wherein the operations furthercomprise sending the route to all of the wireless devices registeredwith the wireless network identified by the service set identifier. 4.The system of claim 1, wherein the operations further comprisemonitoring network waypoints of service set identifiers associated withthe route.
 5. The system of claim 1, wherein the operations furthercomprise assigning a task to one of the wireless devices.
 6. The systemof claim 1, wherein the operations further comprise sending the route toany one of the wireless devices registered with the wireless network. 7.The system of claim 1, wherein the operations further comprisemonitoring network waypoints associated with the route.
 8. A method,comprising: determining, by a server, a count of wireless devicesregistered with a wireless network; querying, by the server, anelectronic database for the count of the wireless devices registeredwith the wireless network, the electronic database electronicallyassociating routes to counts including the count of the wireless devicesregistered with the wireless network; identifying, by the server, aroute of the routes in the electronic database that is electronicallyassociated with the count of the wireless devices registered with thewireless network; and monitoring, by the server, locations associatedwith the wireless devices according to the route identified in theelectronic database.
 9. The method of claim 8, further comprisingsending the route to any of the wireless devices registered with thewireless network.
 10. The method of claim 8, further comprising sendingthe route to all of the wireless devices registered with the wirelessnetwork identified by the service set identifier.
 11. The method ofclaim 8, further comprising monitoring network waypoints associated withthe route.
 12. The method of claim 8, further comprising assigning atask to one of the wireless devices.
 13. The method of claim 8, furthercomprising sending the route to any one of the wireless devicesregistered with the wireless network.
 14. The method of claim 8, furthercomprising monitoring network waypoints of service set identifiersassociated with the route.
 15. A memory device storing instructions thatwhen executed cause a hardware processor to perform operations, theoperations comprising: determining a count of wireless devicesregistered with a wireless network; querying an electronic database forthe count of the wireless devices registered with the wireless network,the electronic database electronically associating routes to countsincluding the count of the wireless devices registered with the wirelessnetwork; identifying a route of the routes in the electronic databasethat is electronically associated with the count of the wireless devicesregistered with the wireless network; and monitoring locationsassociated with the wireless devices according to the route identifiedin the electronic database.
 16. The memory device of claim 15, whereinthe operations further comprise sending the route to any of the wirelessdevices registered with the wireless network.
 17. The memory device ofclaim 15, wherein the operations further comprise sending the route toall of the wireless devices registered with the wireless networkidentified by the service set identifier.
 18. The memory device of claim15, wherein the operations further comprise monitoring network waypointsof service set identifiers associated with the route.
 19. The memorydevice of claim 15, wherein the operations further comprise assigning atask to one of the wireless devices.
 20. The memory device of claim 15,wherein the operations further comprise sending the route to any one ofthe wireless devices registered with the wireless network.